-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RAC] Build a consolidated implementation in Rule Registry (Draft) #101453
[RAC] Build a consolidated implementation in Rule Registry (Draft) #101453
Conversation
d211834
to
739f965
Compare
739f965
to
6733d09
Compare
e087a1a
to
ada916f
Compare
} catch (e) { | ||
this.logger.error( | ||
`error writing bulk events: "${e.message}"; docs: ${JSON.stringify(bulkBody)}` | ||
); | ||
return undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll probably need to return the error here or rethrow it. So we can properly handle errors in the caller methods.
@@ -60,11 +63,16 @@ export class IndexWriter { | |||
} | |||
} | |||
|
|||
public async indexManyNow(docs: Document[]): Promise<estypes.BulkResponse | undefined> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about renaming the methods of this class to make things a little bit more clear?
indexManyNow
-> indexMany
indexOne
-> enqueueOne
indexMany
-> qnqueueMany
897b4a7
to
fa04b8d
Compare
💔 Build Failed
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @banderror |
Ticket: #101016
Summary
This is a draft of the consolidated implementation of index management for RAC indices (see #98912).
TODO:
rule_registry
to the consolidated implementation.Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers